|
On 9 May 2015, an Airbus A400M Atlas cargo plane on a test flight crashed at La Rinconada, Spain, less than from Seville Airport at around 1:00 pm local time.〔〔〔 == Aircraft == The aircraft, serial number MSN023, was on its first pre-delivery test flight and was scheduled to be the third A400M to be delivered to the Turkish Air Force.〔〔 The delivery was scheduled for June 2015.〔(【引用サイトリンク】title=Spanish air force cargo plane on test flight crashes near Seville airport )〕 The aircraft, number MSN23,〔〔 was being flown by an Airbus Defence and Space test crew〔〔〔 and used the callsign CASA423.〔 The pilots had reported that the plane had a technical fault and asked permission to land, but hit an electricity pylon while attempting an emergency landing.〔(【引用サイトリンク】title=Airbus A400M military transporter crashes on test flight, killing four )〕 Tracking data from the Flightradar24 website indicated the plane had veered to the left before coming down and that it had reached a maximum altitude of before descending at a constant speed of about 16,000 feet per minute/.〔(【引用サイトリンク】title=Airbus A400M Transport Plane Crashes in Spain )〕 As of May 2015, Airbus has delivered just 12 of the 174 ordered so far and the programme has been plagued by persistent quality issues, both in the final assembly facility in Spain, and in Germany.〔(【引用サイトリンク】title=Spanish minister defends European aviation after Airbus crash )〕 The Spanish government confirmed on 10 May 2015 that the plane’s flight data recorder and cockpit voice recorder had been recovered.〔(【引用サイトリンク】title=Heroic Spanish farmer dragged survivors out of Seville plane crash )〕 Despite being examined by a joint team from the Spanish ministries of development and defense, the Spanish authorities subsequently passed the recorders to the French military air accident investigation agency BEAD to extract and analyze the data. On 13 May 2015 it emerged that technical issues were slowing retrieval of the crash data; General Bruno Caïtucoli, head of BEAD, reported that "there are technical issues in reading the system, and it is a question of compatibility between systems, so we are still trying to extract data. The extracting system we are using belongs to the French defense procurement agency DGA,” Caïtucoli said, noting that the problem appeared to be a compatibility issue between the recorders and the DGA’s data reading system, rather than an issue with the condition of the recorders themselves.〔(【引用サイトリンク】title=Tech Issues Slow Retrieval Of A400M Crash Data )〕 Several reports suggested that as many as three of the aircraft's four engines failed during the A400M's departure from Seville.〔(【引用サイトリンク】title=A400M Crash Adds To Airlifter Program’s Woes )〕 Airbus initially focused on whether the crash was caused by new management software for the engine-fuel supply, designed to trim the fuel tanks to permit the aircraft to fly certain military maneuvers. There appeared to have been a trimming issue, leading to strong banking that was not recoverable and that the fuel supply was re-established, but not quickly enough for recovery to safe flight.〔(【引用サイトリンク】title=Software Cut Off Fuel Supply In Stricken A400M )〕 Airbus Chief Strategy Officer Marwan Lahoud confirmed on 29 May that incorrectly installed engine control software caused the fatal crash. “The black boxes attest to that there are no structural defects (the aircraft ), but we have a serious quality problem in the final assembly.” Two days earlier, Airbus CEO Tom Enders criticized Spanish agencies for withholding the flight recorder data. “We would like to see the data and compare it with our hypothesis and proceed quickly to understand the causes of accident, so our aircraft can get back into the air,” he told shareholders at the company’s annual general meeting in Amsterdam on May 27. Senior Airbus executive, Fabrice Bregier, said on 30 May 2015 that there was "either a weakness in the test procedure of planes before they fly, or a problem that results from the implementation of these procedures." On 3 June 2015 Airbus announced that investigators had confirmed "that engines one, two and three experienced power frozen after lift-off and did not respond to the crew's attempts to control the power setting in the normal way. Preliminary analyses have shown that all other aircraft systems performed normally and did not identify any other abnormalities throughout the flight."〔 The key scenario being examined by investigators is that the torque calibration parameter data was accidentally wiped on three engines as the engine software was being installed at Airbus facilities, which would prevent the FADECs from operating. Under the A400M's design, the first warning pilots would receive of the engine data problem would be when the plane was 120 meters (400 feet) in the air; on the ground, there is no cockpit alert.〔(【引用サイトリンク】title=A400M probe focuses on impact of accidental data wipe )〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「2015 Seville Airbus A400M Atlas crash」の詳細全文を読む スポンサード リンク
|